Skip to content

Details output option for list #5939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
JohnMcPMS merged 10 commits into from
Jan 7, 2026
Merged

Details output option for list #5939

JohnMcPMS merged 10 commits into from
Jan 7, 2026

Conversation

@JohnMcPMS
Copy link
Member

@JohnMcPMS JohnMcPMS commented Dec 19, 2025

Change

The new experimental feature listDetails enables a new option for the list command, --details. When supplied, the output is no longer a table view of the results but is instead a series of show like outputs drawing data from the installed item.

An example output for a single installed package is:

> wingetdev list Microsoft.VisualStudio.2022.Enterprise --details
Visual Studio Enterprise 2022 [Microsoft.VisualStudio.2022.Enterprise]
Version: 17.14.21 (November 2025)
Publisher: Microsoft Corporation
Local Identifier: ARP\Machine\X86\875fed29
Product Code: 875fed29
Installer Category: exe
Installed Scope: Machine
Installed Location: C:\Program Files\Microsoft Visual Studio\2022\Enterprise
Available Upgrades:
  winget [17.14.23]

When there are multiple results, the identity line is prefixed with the standard (N/M) format string used in multi-package operations elsewhere.

If sixels are enabled and supported by the terminal, an icon for the installed package will be shown. This currently models the mechanism used by winget-pkgs to extract the icons and by the show command to select the appropriate one to display. It is using the same code in the same manner and should be representative of what would be shown to the user if it were doing the full round trip through the repository/cache/show command.

@JohnMcPMS JohnMcPMS requested a review from a team as a code owner December 19, 2025 19:12
@denelon denelon linked an issue Dec 19, 2025 that may be closed by this pull request
Display the path to an installed package #2298
Closed
@denelon
Copy link
Collaborator

denelon commented Dec 19, 2025

image

florelis
florelis previously approved these changes Jan 6, 2026
View reviewed changes
src/AppInstallerCLICore/Workflows/ShowFlow.cpp Outdated
return;
}

auto lines = Split(value, '\n');
Copy link
Member

@florelis florelis Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just call the version that takes a container after this?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Issue-Feature This is a feature request for the Windows Package Manager client. label Jan 6, 2026
@JohnMcPMS JohnMcPMS merged commit 6a2762e into microsoft:master Jan 7, 2026
9 checks passed
@JohnMcPMS JohnMcPMS deleted the show-list branch January 7, 2026 19:20
@DHowett
Copy link
Member

DHowett commented Feb 4, 2026

I'm finding that winget show doesn't sixel icons any longer, but winget list --details does? was that intended (and related to this PR?)

@JohnMcPMS
Copy link
Member Author

JohnMcPMS commented Feb 4, 2026

I'm finding that winget show doesn't sixel icons any longer, but winget list --details does? was that intended (and related to this PR?)

winget show is reliant on the winget-pkgs validation+cache service to extract icon information and merge it into the resulting manifest. If there are issues in that complex chain of events there may not be an icon available to show.

winget list --details leverages the same code that is run during validation's detonation phase to extract the icon, but does so on your local machine in real time. Seeing an icon with list --details means that this code is working for the install and so it probably should work for the package in winget-pkgs... but again there are many more moving parts to get that icon out to the world.

@DHowett
Copy link
Member

DHowett commented Feb 4, 2026

Totally makes sense. Chatted with Demitrius - sorry to randomize you John!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@florelis florelis florelis approved these changes

Assignees

No one assigned

Labels

Issue-Feature This is a feature request for the Windows Package Manager client.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Display the path to an installed package

4 participants

@JohnMcPMS @denelon @DHowett @florelis